@ltroussellier could you take a look at this PR for adding an esgvoc manifest to obs4REF and see if this can be added to esgvoc now?

The guidance I have includes adding all the CV values here to the WCRP universe as well. I'm attempting to do this, but have noticed the following:

• Obs4REF nominal resolutions have no space in the value (i.e 5km) versus the value in the WCRP-universe that includes a dash (i.e 5-km). Should this be changed in Obs4REF to match the universe?
• Obs4REF folders (e.g activity_id, variable_id) do not match their universe counter parts (e.g activity, variable) in the naming convention. Is this acceptable for the schema or should this be changed to match the universe?
• Other Obs4REF folders have similar naming differences (grid_label -> grid, references -> reference)
• The values for source_type in Obs4REF do not appear to be similar to the equivalent in the universe - is this the correct set of values for source type or is this a different facet's values?

These also apply to the obs4MIPs repo

Hum,

• the _CVs directory is useless for esgvoc, it is meant as a archive (for tracability) .. So i dont mind, you can do whatever on it. But esgvoc will NOT read it (not the good structure)

• the manifest, good try, but the manifest (at least in CMIP7 and other projects) is dealt by CI/CD when change are accepted from esgvoc_dev into main/esgvoc (the prod branch).

Obs4REF nominal resolutions have no space in the value (i.e 5km) versus the value in the WCRP-universe that includes a dash (i.e 5-km). Should this be changed in Obs4REF to match the universe?

this one i have to think more about it

Obs4REF folders (e.g activity_id, variable_id) do not match their universe counter parts (e.g activity, variable) in the naming convention. Is this acceptable for the schema or should this be changed to match the universe?

Other Obs4REF folders have similar naming differences (grid_label -> grid, references -> reference)

The values for source_type in Obs4REF do not appear to be similar to the equivalent in the universe - is this the correct set of values for source type or is this a different facet's values?

The mismatch between Obs4REF folder names (e.g., activity_id, variable_id) and their corresponding Universe counterparts (e.g., activity, variable) is handled through the 000_context.json mapping.
For instance : https://github.com/Climate-REF/Obs4REF_CVs/blob/main/source_type/000_context.jsonld
this context file defines the relationship between an Obs4REF directory and its corresponding Universe directory. For example, in the source_type directory, the 000_context.jsonld file specifies the @base mapping, indicating that this directory corresponds to obs_type in the Universe.
Therefore, the directory names do not need to be identical. This approach allows different projects to use their own naming conventions while still referencing the same concepts in the Universe.

Great, thanks for the comments. Some of these will be addressed in a meeting tomorrow, specifically about the nominal resolutions, plus the values for source_type that may be incorrect as well.